@jaydson what do you think about changing the contributing guide a bit? I believe contributors could just send PRs against the src branch, and then you, I or another collaborator can update the master branch on our discretion. The main pros I see are:

• Takes away the burden from collaborators of sending two PRs per contribution
• Takes away the burden from us of reviewing the PR of the master branch
• The master PRs can get outdated very fast, they become useless if we merge anything else in the src branch.

I believe we can just use the src branch as a regular repository (commit, merge PRs, etc.) and then update the master branch automatically based on the latest src commit. We can make a shell script or maybe a Grunt task for deploying. Perhaps even a CI/post-receive Git hook. This way we can cut down half of the "How to contribute" section as collaborators won't need to commit to the master branch anymore.

Thoughts?

Yep, agree.
Let's do it.
Please file an issue for changing the contributing guide.

About the Grunt task, we need to evolve Harmonic to support deployment.

@jaydson oh yes, right, we do have an issue open involving deployment in the Harmonic repository.

#17

so I just PR md tothe src branch?

Oh, I see , that is after the matter :)

so I just PR md tothe src branch?

Yes.

I've already accepted your other PR (#15) and merged it into 3434b7a, so you didn't have to open a new one. :)